Zen

Translation

English type: Plain text
The `+dir+` file generated by GNU Hello build script indexes all texinfo pages in your system. Because the installed pages differ among systems, the file cannot be prebuilt and packaged. Instead it needs to be created and updated when the package is installed. The update is automatically performed by RPM triggers in `+info+` binary package of https://src.fedoraproject.org/rpms/texinfo[texinfo source package].
0/4150 · 415

Sign in to save the translation.

English Spanish Actions
%install
%make_install
%install
%make_install
%files
%{_bindir}/hello
%{_mandir}/man1/hello.1.*
%doc AUTHORS ChangeLog NEWS README THANKS TODO
%license COPYING
%files
%{_bindir}/hello
%{_mandir}/man1/hello.1.*
%doc AUTHORS ChangeLog NEWS README THANKS TODO
%license COPYING
%changelog
%autochangelog
%changelog
%autochangelog
Downloading source
Descargar la fuente
Download sources and check that you now have them:
Descargar las fuentes y comprobar que ahora las tiene:
$ spectool -g hello.spec
$ ls *.tar.gz
hello-2.10.tar.gz
$ spectool -g hello.spec
$ ls *.tar.gz
hello-2.10.tar.gz
Building the Package
Construir el Paquete
$ fedpkg --release f{MAJOROSVER} mockbuild
$ fedpkg --release f{MAJOROSVER} mockbuild
This command fails because of unpackaged files.
Este comando falla debido a archivos no empaquetados.
Installing files
Instalar archivos
As in part 1, we will go through the file list one by one. Run `fedpkg --release f{MAJOROSVER} mockbuild` again after each change to see the progress.
Como en la parte 1, iremos a través de la lista de archivos uno por uno. Ejecute`fedpkg --release f{MAJOROSVER} mockbuild` otra vez después de cada cambio para ver el progreso.
Texinfo pages
Páginas Texinfo
Installed (but unpackaged) file(s) found:
/usr/share/info/dir
/usr/share/info/hello.info.gz
Installed (but unpackaged) file(s) found:
/usr/share/info/dir
/usr/share/info/hello.info.gz
These are https://www.gnu.org/software/texinfo/[Texinfo] pages. Texinfo is a documentation system like man pages, but much less common. Texinfo pages are handled much in the same way as man pages. The directory is defined by the default macro `+{_infodir}+`, so the Texinfo manual can be added as follows:
Estas son las páginas https://www.gnu.org/software/texinfo/[Texinfo]. Texinfo es un sistema de documentación parecido a las páginas de manual. El directorio está definido por la macro predeterminada `+{_infodir}+`, de modo que el manual Texinfo se puede añadir como sigue:
%files
⋮
%{_infodir}/hello.info.*
%files
⋮
%{_infodir}/hello.info.*
The `+dir+` file generated by GNU Hello build script indexes all texinfo pages in your system. Because the installed pages differ among systems, the file cannot be prebuilt and packaged. Instead it needs to be created and updated when the package is installed. The update is automatically performed by RPM triggers in `+info+` binary package of https://src.fedoraproject.org/rpms/texinfo[texinfo source package].
 
To prevent from installing the `dir` file, remove it from the _buildroot_ at the end of the `%install` section with `rm` command.
 
However, GNU Hello build script only generates the `dir` file if `info` package is installed during the build. Blindly removing the file would raise an error if the `hello` package were built on a system without `info` package. To handle both cases, delete the file if it exists:
 
%install
⋮
test -f %{buildroot}/%{_infodir}/dir && rm %{buildroot}/%{_infodir}/dir
 
Translations
 
Installed (but unpackaged) file(s) found:
/usr/share/locale/bg/LC_MESSAGES/hello.mo
/usr/share/locale/ca/LC_MESSAGES/hello.mo
/usr/share/locale/da/LC_MESSAGES/hello.mo
⋮
 
Since our program uses translations and internationalization, we are seeing a lot of undeclared i18n files. The xref:packaging-guidelines::index.adoc#handling_locale_files[recommended method] to declare them is:
 
Add the required build dependency with `+BuildRequires: gettext+`.
 
Find the filenames in the `+%install+` step with `+%find_lang %{name}+`.
 
Install the files with `+%files -f %{name}.lang+`.
 
After these changes, build succeeds.
 
Running tests
 
GNU Hello, like many other projects, includes an automated test suite in the sources. If at all possible, the test suite should be run during the rpm build. This helps ensuring that a working build was produced. This is done by adding the test suite invocation to specfile `+%check%+` section, which comes after `+%install+` in order. In GNU Hello's case:
 
%check
make check
 
Run a mockbuild again and check the output to ensure that the tests were actually run. Something like this should be somewhere in the output:
 
============================================================================
Testsuite summary for GNU Hello 2.10
============================================================================
# TOTAL: 5
# PASS: 4
# SKIP: 1
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
 

Loading…

User avatar None

String added in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Packaging_Tutorial_2_GNU_Hello
  3. Spanish
The `+dir+` file generated by GNU Hello build script indexes all texinfo pages in your system. Because the installed pages differ among systems, the file cannot be prebuilt and packaged. Instead it needs to be created and updated when the package is installed. The update is automatically performed by RPM triggers in `+info+` binary package of https://src.fedoraproject.org/rpms/texinfo[texinfo source package].
 
6 days ago
Browse all string changes

Glossary

English Spanish
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./@]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"
Source string location
./pages/Packaging_Tutorial_2_GNU_Hello.adoc:139
String age
6 days ago
Last updated
6 days ago
Source string age
4 weeks ago
Translation file
po/es/master/pages/Packaging_Tutorial_2_GNU_Hello.po, string 32